home *** CD-ROM | disk | FTP | other *** search
- Thanks for considering LiteComm, version 6.0, as part of your
- programming tools.
-
- ADDED DOCUMENTATION
- Registered users please note that the documentation for the protocol
- engines is not contained in the printed documentation. Please see the
- file proto.doc for protocol engine documentation.
-
- LIBRARY NAMES
- The documentation is unclear about library file names. Here is some
- additional information.
-
- MICRROSOFT C
-
- mscc?.lib Basic LiteComm Libraries
- msclcp?.lib Protocol Engines
-
- TURBO C
-
- tcomm?.lib Basic LiteComm Libraries
- tclcp?.lib Protocol Engines
-
- The final letter in the library name denotes the model that the library
- supports, c - compact, l - large, m - medium, and s - small.
-
- ADDITIONAL FILES
- The packing list omits the file lcsrc.exe that contains the LiteComm
- source code. This file is present ONLY in the registered version.
-
- REMAKING LIBRARIES
- The documentation omits a reference to the batch files included that are
- designed to make library maintenance simpler. These file are:
-
- TMAKE.BAT Make new LiteComm libraries - Turbo C
- TPMAKE.BAT Make new protocol libraries - Turbo C
- MMAKE.BAT Make new LiteComm libraries - Microsoft C
- MPMAKE.BAT Make new protocol libraries - Microsoft C
-
- For examples, to make a new, compact model library under Microsoft C, simply type the
- commands
- MMAKE C
- MPMAKE C
-
- The corresponding commands for Turbo C are
- TMAKE c
- TPMAKE c
-
- Please note that the case of the model designation, C in the above
- example, is significant. Microsoft C requires the use of upper case
- models, while Turbo C requires the use of lower case.
-
- Also note that these batch files assume that the utilities pkzip and
- pkunzip are available somewhere on the system's path. You may, of
- course, sunstitute other file compression utilities.